5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
- Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-4: Understanding Process Design

Processes Compared With Programs


A process is very similar to a program in traditional data processing systems, in that:

You execute a process to perform one or more related functions or activities.

A process is the smallest unit of an application that can be executed separately.

A process consists of a series of detailed instructions performed in a specified sequence. These instructions consist of process specifications, their associated painted images, data dictionary references, and ILF routines.

APPX compiles the process source specifications into instructions more suitable for machine execution.

There are, however, some significant differences between a process and a traditional program, including the following:

A program consists entirely of line-by-line procedural coding, while a process is comprised of an integrated set of specifications.

You must compile a program as a separate step before executing it but a process is compiled automatically at runtime, if required.

A program must include a detailed definition of the files and fields that are referenced, whereas all data referenced by a process (including local temporary data) is defined in the data dictionary.

In a program, you must explicitly control when each instruction is executed, while an APPX process automatically executes based on the specifications.

You use a standard editor to develop and modify a program, while in APPX you use the specification screens to guide development.

Each program represents a separate file, but all the processes for an entire application are stored in a set of APPX design files.

You access the process definition facility from the Application Design menu. The first screen you see allows you to specify the type and name of the process you are defining or editing. After you identify the process, you see displayed the remainder of the specifications that are applicable to the type of process (menu, input, etc) you selected. From this point on, APPX moves you automatically through the family of screens that comprise the process definition facility. On the facing page is a schematic diagram of the process definition design components.

The Process Family

Application Design Manual                                         "Powered by Appx Software"

62

©2006 By APPX Software, Inc. All Rights Reserved